Gitana: a SQL-based Git Repository Inspector

International audienceSoftware development projects are notoriously complex and difficult to deal with. Several support tools such as issue tracking, code review and Source Control Management (SCM) systems have been introduced in the past decades to ease development activities. While such tools efficiently track the evolution of a given aspect of the project (e.g., bug reports), they provide just a partial view of the project and often lack of advanced querying mechanisms limiting themselves to command line or simple GUI support. This is particularly true for projects that rely on Git, the most popular SCM system today. In this paper, we propose a conceptual schema for Git and an approach that, given a Git repository, exports its data to a relational database in order to (1) promote data integration with other existing SCM tools and (2) enable writing queries on Git data using standard SQL syntax. To ensure efficiency, our approach comes with an incremental propagation mechanism that refreshes the database content with the latest modifications. We have implemented our approach in Gitana, an open-source tool available on GitHub

Effort estimation of FLOSS projects: A study of the Linux kernel

This is the post-print version of the Article. The official published version can be accessed from the link below - Copyright @ 2011 SpringerEmpirical research on Free/Libre/Open Source Software (FLOSS) has shown that developers tend to cluster around two main roles: “core” contributors differ from “peripheral” developers in terms of a larger number of responsibilities and a higher productivity pattern. A further, cross-cutting characterization of developers could be achieved by associating developers with “time slots”, and different patterns of activity and effort could be associated to such slots. Such analysis, if replicated, could be used not only to compare different FLOSS communities, and to evaluate their stability and maturity, but also to determine within projects, how the effort is distributed in a given period, and to estimate future needs with respect to key points in the software life-cycle (e.g., major releases). This study analyses the activity patterns within the Linux kernel project, at first focusing on the overall distribution of effort and activity within weeks and days; then, dividing each day into three 8-hour time slots, and focusing on effort and activity around major releases. Such analyses have the objective of evaluating effort, productivity and types of activity globally and around major releases. They enable a comparison of these releases and patterns of effort and activities with traditional software products and processes, and in turn, the identification of company-driven projects (i.e., working mainly during office hours) among FLOSS endeavors. The results of this research show that, overall, the effort within the Linux kernel community is constant (albeit at different levels) throughout the week, signalling the need of updated estimation models, different from those used in traditional 9am–5pm, Monday to Friday commercial companies. It also becomes evident that the activity before a release is vastly different from after a release, and that the changes show an increase in code complexity in specific time slots (notably in the late night hours), which will later require additional maintenance efforts

Scenario-Based Design Theorizing:The Case of a Digital Idea Screening Cockpit

As ever more companies encourage employees to innovate, a surplus of ideas has become reality in many organizations – often exceeding the available resources to execute them. Building on insights from a literature review and a 3-year collaboration with a banking software provider, the paper suggests a Digital Idea Screening Cockpit (DISC) to address this challenge. Following a design science research approach, it suggests a prescriptive design theory that provides practitioner-oriented guidance for implementing a DISC. The study shows that, in order to facilitate the assessment, selection, and tracking of ideas for different stakeholders, such a system needs to play a dual role: It needs to structure decision criteria and at the same be flexible to allow for creative expression. Moreover, the paper makes a case for scenario-based design theorizing by developing design knowledge via scenarios

Measuring the Development Performance of Integrated Computer Aided Software Engineering (ICASE): A Synthesis of Field Study Results from The First Boston Corporation

This paper reports on a multi-year field study conducted at the First Boston Corporation to investigate the performance of its object and repository-based integrated computer aided software engineering (I-CASE) tool called High Productivity Systems (HPS). We present productivity and software reuse results for: * three closely monitored small-scale I-CASE pilot projects; and, * twenty large-scale investment banking projects built during the first two years of the I-CASE tool's deployment. Our results offer perspective on the potential for order of magnitude gains in software development productivity when reusable software development approaches are applied. They also suggest the need for new measurement and management approaches to foster improved software development performance in the I-CASE world.Information Systems Working Papers Serie